Glad you mentioned about:memory. I usually read the changelog when they push out a release but somehow I missed that. This is a very nice breakdown of the memory.
Twitter loads a huge (several megabytes of source code, last I checked) blob of JS into every single twitter.com page. Then it loads a bunch of data, including what is basically a custom layout engine for some of their UI widgetry.