I'll try to be brief, because, as I said before, I'm just not having these problems. My browsing habits probably differ from most. I try to minimize malicious 'Web Content' as much as possible. That means:
* Not keeping cookies & 'local storage' around when I'm on a broadband connection anyway. Stale data causes problems.
* Running Glimmerblocker and killing a LOT of malicious (to me) javascript and 'refresh' processes (websites that try to 'game' pageviews by constant page refreshing. Also killing any link that points to /ad/ as they are doing the same thing.
* No Flash. That cuts out the rest of the ads. If you need Flash, do the John Gruber thing and just install Chrome.
* Not so many tabs open, because (as again with misbehaving web sites, their scripts & bots) each of these tabs would be still running.
Now to where things are going. I think Apple foisting things into a 'Web Content' process was supposed to be a subtle hint to the users as to where the problems lie. "Web Content" as a name was no accident. So here are my educated guesses. I could be wrong.
Apple has been systematically cutting variables that inject into the OS & apps like Safari (and Mail, which uses Safari components to render). First they cut 3rd party Haxie type things, then input managers. They discourage things like SIMBL. And then on the iOS side there was that 'Letter from Steve' over Flash. Are you having these problems on your iOS things? No.
Apple probably should test with more tabs in Safari. But the implicit UX is that you won't open 'as many' tabs, that you will use Reading List. Note that RSS was also killed in Safari (and Mail which uses Safari webkit views). Yes there are still web plugins, but HTML5 is supposed to take over a lot of that functionality.
As far as Google Chrome goes, on my Mini I've been able to bog it down just like Safari. Just open 10 tabs of Youtube without a plugin blocker. Google, for its part will be 'locking down' rogue javascript extensions: From the next version (maybe now?) you can only load Chrome Extensions from their 'Store'. And they prominently feature plugin & Javascript blockers in their store.
The only final thing that I can add is that more visual display, as well as 'number crunching' is being handed off to the GPU. Newer machines benefit from this, older machines & MacBook Pros on battery (using the integrated video) will just bog down. 2 gigs for 10 or so tabs, *depending on the content* may not be out of line.
Apple *may* produce a fix for "newer" machines. But for the 'very old' it may be better to stay on 10.6 or 10.7. The one saving grace is that Apple *does* listen, so if enough folks hit 'Feedback' they will address the issue. In their own way. This link might be helpful: http://pondini.org/OSX/BugReport.html
Those are just the breaks.
-Leo "any more than 5 tabs, to Instapaper they go" M.