I just finished entering a comment above suggesting people should give it another try; I have 100 or so tabs open and 500MB footprint after using it all day, with version 13 (I just stick with the release update channel) in win7.
In my experience they've very clearly fixed whatever the main memory issue was that affected my experience -- but not yours. Though -- the windows versions may get a bit more testing....
I'm running Firefox 15 / Iceweasel 10 on Ubuntu and Debian respectively, watching VIRT (total virtual memory size). Currently sitting at 2.3 GB, FML.
There's a utility called 'pmap' that you can use to display the memory mapped files and subtract it from the total etc.
Finding out how much memory a program is using is surprisingly tricky to compute. Good luck.
Sorry, but that's totally nuts.
Mozilla have been claiming "we've solved the memory leak problem" about as long as Microsoft have been claiming "we've solved the virus/security problem", or so it seems. With about the same level of credibility.