Side: Python, Django, web.py, sqlalchemy, D, Javascript/jQuery, Erlang, Postgresql, Mysql, Sqlite, CouchDB, Mercurial, Git
Work: Perl, Bash, Python, PHP, Javascript/jQuery/in house stuff, ASP, Java/Jboss/Fast/JSP, ColdFusion, Soap, XML/XSL, Sql Server, Oracle, Mysql, Subversion
Huge lists on both sides, but there's a main difference: If something is broken over work, I have to fix. I don't exactly know Java or ColdFusion that much, but if the Java guy is away and something needs to be done, I know enough to poke around and consult Google.
On the Side: I don't exactly know all of D, Erlang and CouchDB, but I have fun coding small things on each language from time to time, doing stuff on Project Euler. I wouldn't accept a paying job which required Erlang, for example, but I made simple a distributed crawler just to see what the platform is capable of. I think I know enough of each to at least understand its strengths and weakness on a higher-level, to know when it could be used as a solution. When I want to do something more serious, I choose Python.
Anyway, to trim the lists a little, I would say Python on Side, and PHP on Work. These languages get 75% of my time.