Guys, you´re missing the point regarding the talk about battery usage.
Sure, there are many things that eat up battery life and so any app that uses more of the device´s functionalities and ressources will drain the battery quicker than when its in idle mode chilling.
The point regarding flash being special there is that flash is using up way more resources when handling way simpler stuff compared to when doing the same as a native app in well done manner or even when doing it using a better middleware solution.
Again, Adobe can say this is not true but anyone with a highend desktop who has played some for flash terms in depth action intense 2d games can have a look at his memory and cpu usage and easily see that flash is a heavy ressource drainer when a machine uses up that much resources to run basic content while when done in other ways a ten year older machine could easily run, let´s say starcraft with way more going on easily.
To me personally the battery drainer side doesn´t matter that much itself, to me those points that are most valid regarding what Apple said against flash are:
-lack of performance and stability compared to other solutions
-with adobe´s way of doing cross platform deploy one can´t use the device´s capabilities to the max at all. Even when disregarding the performance side, just looking at the api/ software side this is quite a bummer:
When going the Adobe Flash/Air deploy way for devices one basically can only use those features and those api/sdk elements possible on the devices which Adobe implemented and exposed via its own API.
That means many features of the device and device´s sdk/ OS can not be used. If you´d for example have a look at which features of the iPhone sdk Adobe´s exporter supported you´d see that one can´t do many, many things in an app made with the Adobe exporter which are possible with the iPhone sdk, why, even many things seen as total standard for every iPhone app, because Adobe hasn´t integrated them in their AS api.
Likewise it could also be expected the same is the case for Android OS deploy and would also be the case when iPhone OS 4.0 ships which has many new features, which then of course again people using the Adobe exporter would not be able to use until if ever Adobe implements and exposes them via their own api.
As developer it annoys me when i can´t use all the features of a device and its OS unless Adobe feels like implementing them on their end and seeing it from Apple´s stance i totally understand it that they wouldn´t be happy with Adobe dictating when app developers can use features Apple has created for its devices and OS.
-Another thing i find fascinating about this whole discussion is that i´ve seen no one else bring up how limiting Adobe is towards the developer community.
Adobe and Adobe close people have done a good job at blaming Apple all the way for wanting to control what developers develop how for which platform and Adobe on the other side would be oh so generous in allowing oh so much freedom to develop anything for anything.
Is Adobe really giving us so much choice?
Last time i checked they were the company who´d like everyone to use their tools no matter for which platform they develop and they go even further in controlling things by not just controlling which tools you ideally use to create content no matter for what, nay, they also dictate which language you use, cause they haven´t even considered supporting AS1 and 2 onwards (not even to think about adding support for more languages, haha), nay, with the flash/air deploy to devices you´re forced to only use AS3 on many.
So where´s the freedom of choice there?

