I had (and still have on 10.6.4) the same issue you guys described. I bought a 17" i5 MacBook Pro (with the high-res display, if that makes a difference) basically the day they came out, so it's still covered under warranty.
When I first noticed the corruption I figured out that it only happens using the Intel graphics - if I unchecked "Automatic graphics switching" in the Energy Saver pref pane, it almost instantly went away, but came back as soon as I let it switch back to Intel graphics.
So I took it to an ASP and told them I believed the IGP was bad. I couldn't show them screen shots because all I'd captured was a black box the size of my desktop - no idea how that happened. I also got a kernel panic minutes after deciding I was gonna take the laptop to the shop, so I couldn't show them what was wrong. They were super nice about it and replaced the logic board anyway, even though they couldn't reproduce my issue, so kudos to them.
But now, less than a week later, the issue reappeared, and I did some more in-depth testing and figured out it was indeed Flash (10.1) corrupting my graphics - opening Activity Monitor and force quitting the Flash plugin task, then toggling graphics switching off and on again fixes the corruption reliably. Even without the toggling, it will gradually go away, presumably as OS X overwrites Flash's junk with actual display data again. The downside to this is that for Flash to work again, you'll have to restart Safari. Not a huge problem if you use Glims or any other plugin that restores open tabs, but still a nuisance...
I have
not tested any browser except Safari, but it seems pretty clear to me that Flash is writing in parts of the RAM it really shouldn't be, namely the shared VRAM parts. I really hope Adobe - and possibly Apple, too, if there's a flaw in Safari - manage to fix this problem soon...