I think the reality is ...
Google screwed the pooch when it came to having non-native apps (aka framework based) be accelerated *efficiently* in pre-3.0 days. Some operations did go to the GPU then, but the fact was some sub-view getting invalidated caused much more rendering than was needed.
In 3.x they added an option to have apps say "please accelerate me", but that option is an "opt-in". That choice was done for back-compatibility (not *every* operation in the framework is allowed to be accelerated which means some apps could break).
In reality, most of the "OS" level apps did an opt-in, but not everything. I also doubt general "market" apps do the opt-in (unless they are 3.x+ only).
In 4.x, it's going to be an "opt-out" strategy. So, if an app is broken in ICS, then the developer needs to update/fix their code (IFF necessary, since most are likely to "just work").