Mmm! Pass the kool-aid!
Full disclosure: I work for Appcelerator, but my opinions are my own, yadda yadda.
"Really? Which ones? What does the sound of Apple getting increased attention sound like?"
http://www.theregister.co.uk/2010/05/03/doj_and_ftc_exploring_apple_antitrust_inquiry/
http://www.theregister.co.uk/2010/06/10/apple_gov_probe/
http://www.theregister.co.uk/2010/08/11/eu_investigation_apple/
It sounds like web links, really. Although in all honesty, I doubt that was the primary motivator. While the "No. That is all." comment is technically correct, the issue isn't facts in as much as perception. The app store rules (Or rather, their unknown state and the verbiage about interpreted code) served as FUD against Apple. Apple is heavily pushing the iPod touch as a games platform. But most games DO use interpreted code, from entire setups like Unity to more minimal embedded interpreters like Lua. This is done everywhere, in all platforms, not only for portability but for rapid development and stability (so you don't have to worry about memory management of dialog trees), so the specter of an app being rejected for this is enough to scare prospective developers away. And that's bad business to both devs and Apple.
I am led to believe that Adobe's income of CSS for the Mac is significant, and that Adobe would not cut off its nose to spite its face. More accurately, I think that various teams inside Adobe are independent, and so Photoshop would not sacrifice its revenues in revenge for Flash.
And while the Flash issue did hog center stage, it's a bit of a red herring in terms of interpreted code. Or rather, the fact that it has code interpretation is orthogonal to most issues mentioned in Jobs' "Thoughts on Flash." One of the 'painful experiences' mentioned may be referring to when Mac OS X came out, and some third party layers, even non-cross-platform ones written in C or C++, were slow to support the changed API.
What will be watch-worthy is how Adobe reacts, and moreover, the fate of flash-built apps going forward. Will they go through unscathed? Will they be rejected for different reasons? Will they be stuck in review limbo, neither approved nor rejected? Issues of stability, speed, and UI are all valid reasons for rejection that ensnare native apps, and could possibly be used against flash apps.