You're welcome.
I'm sorry, I should have explained to you something important. Java3D 1.5.2 uses a native renderer based on Direct3D under Windows whereas Java3D 1.6.0 uses JOGL 2.0 everywhere. As a consequence, if the Java2D pipeline based on Direct3D is enabled, there is a risk of conflict at driver level with OpenGL (and then with JOGL). You're not forced to enable the Java2D pipeline based on OpenGL but it is highly recommended to disable the pipeline based on Direct3D for JOGL applications. I advise you to disable DirectDraw too:
-Dsun.java2d.noddraw=true
I didn't think that your problem came from this thing. Thanks for the feedback, really. It would be cool to write a sentence about that in the JOGL users guide.