These options enable more DirectDraw and Direct3D functionality in the Java2D implementation. DirectDraw/D3D and OpenGL are fundamentally incompatible at the driver level. I have seen many problems on various vendors' cards when they are combined at all in the same application. The only way to guarantee robust behavior of JOGL on Windows platforms is to completely disable Java2D's use of DirectDraw and D3D. The only Java2D command-line option you should specify is -Dsun.java2d.noddraw=true.
I tried taking the unmodified jcanyon JOGL demo source, building it on Java 1.6 beta 2 (with JOGL beta 5) and running it, and comparing it to Java 1.5.0_07 running with -Dsun.java2d.noddraw=true (and without the opengl pipeline). This is with the AWT/heavyweight rendering. The slowdown is less obvious in heavyweight, but is still present. Once you approach the canyon, Java 1.5 beats Java 1.6 by a few fps consistently. With the extra slowdown involved in lightweight rendering, the "few fps" slowdown remains but becomes a much higher percentage. (eg. heavyweight I'd get, perhaps, 17fps->14fps, while in lightweight I'd get 8fps->5fps.)
I guess I'll start with filing a JOGL bug, since this slowdown brings the rendering speed below the threshold at which it appears to be "animation" and turns it into a fast slideshow, and I'd really like to embed 3D in this non-opengl-mode, lightweight application.