Adobe's response, from a game-theoretic perspective, is to adhere to

   3.3.1 — Applications may only use Documented APIs
   in the manner prescribed by Apple and must not use
   or call any private APIs. Applications must be 
   originally written in Objective-C, C, C++, or 
   JavaScript as executed by the iPhone OS WebKit 
   engine, and only code written in C, C++, and 
   Objective-C may compile and directly link against
   the Documented APIs (e.g., Applications that link 
   to Documented APIs through an intermediary translation 
   or compatibility layer or tool are prohibited).

by simply generating Objective-C as their Object Code. Developers then compile this for their target platform (iPhone) and stay within the bounds of 3.3.1. I see Apple is trying to put a kibosh on this with the "originally written" clause, but, that will be a stretch to enforce.