No need for a flame war, because you're apparently unaware that Java3D is basically just an abstraction layer for calls to OpenGL or DirectX. The application doesn't use Java2D or such for rendering - it's going to the hardware for rendering. Result: it's plenty fast.
The fact that there isn't a slow all-Java fallback option (like, say, in the Java Media Framework) is why the original poster was asking about Java3D - any Java3D implementation *requires* native code to tie into OpenGL or DirectX on that platform, and there isn't a version for Mac OS X yet.
This comes up on Apple's java-dev list a lot.