I fear the auto-update feature combined with multitasking will drastically reduce the typical battery life of an iOS device.
Another point is that unless updates are being pushed constantly, I don't see why it would suddenly kill battery life more so than if they were pulled - it is just the timing of when to do updates (over time or "update all" as a batch - I doubt people actually distribute their updates according to battery usage).
Still, it would be nice to have more composability in apps. I'm working on a UI plugin / framework for apps and I really wish that I could do incremental updates without developers having to redeploy their entire app. If only you could include app dependencies so that when you downloaded an app that used Dropbox, for example, it would download Dropbox too. That way, when Dropbox wanted to update their SDK, they could just push an update to their app instead.
The composability point is interesting. I like the idea of dependencies, and I've used url schemes to do it. You can test for whether or not an app is installed (given that it has a scheme) by testing invoking - (BOOL)canOpenURL:(NSURL *)url from UIApplication. Something interesting would be for Apple to require that each app have a custom URL scheme, and possibly generate them from a unique app identifier.
Also makes a lot of sense from a user's perspective. Click-to-update is so last decade.
One of the biggest pains I think we face as developers is software fragmentation. So far Apple has done a very good job of having users update versions of iOS and keeping consistent with hardware specifications - it's probably one of the top three main drivers for why I develop primarily for iOS (sometimes solely for iOS). I'm thinking this reinforces that build-for-iOS-first mentality for developers. If the quality of apps is such a large factor in what's keep users loyal to the platform, this is an important point.