If it doesn't matter because you can use C or C++ for critical parts... well you can do that from Objective-C too, and it's trivial. It's far simpler than working through a JNI bridge.
I'm still puzzled by the decision, given the horror of J2ME and the failure of Java on the desktop. Why not C++?
I agree with you on the garbage collector, though. It really slows down things by thrashing on multilevel caches, despite generational GC. I would really like to perhaps see something that gave you a choice of either reference counting + destructors, or, garbage collection. I can't see how you could make mixing libraries written for one or the other style work with an arbitrary ref-cnt / GC selection, though.
I'd probably miss exception handling in any event, as well.
Damn trade offs. I want it all, and I don't want to pay for it!