>Once upon a time Java was one of the preferred methods for writing Mac OS apps: Apple clearly doesn't want that anymore.
Apple just doesn't see enough benefit in continuing their own JVM development. The primary reason that Java was the preferred method was purely because of the portable nature of Java code, and the fact that Mac OS9 and OSX didn't really have enough marketshare to make full ports feasible. Since OSX has a fairly decent marketshare at this point, it's an easier argument to make a native port over multiplatform, portable code like Java.
One of the issues with Java on OSX was that, most of the time, you couldn't actually code to the latest version of Java, because Apple was months(or even years) behind on implementing new JVM and Java language specs.
It took Apple about a year and a half to update their JVM to 1.6 after that was released. Here's a timeline for Apple's historical Java releases:
http://stuffthathappens.com/blog/2007/10/28/os-x-java-defini...
Java 6 support was released in May, 2008: http://support.apple.com/kb/ht1856
Given that history, and the fact that iOS is primarily objective C, it's really no surprise that Apple decided to depreciate the JVM from their OS.