Java WebStart feature requires a large amount of code be downloaded. Aligns with
the overall modularity and "small footprint" goals of GlassFish V3. Ideally,
only the code required to service the application should be required.
The general modular approach for v3 might help a great deal with this simply by
structuring the code much more effectively. (In v2 and earlier the ACC required
several large GlassFish JARs simply because each contained a few classes that
the ACC needed.)
To work effectively in Java Web Start launches we might need to provide a custom
hk2 Repository implementation that works with the Java Web Start API to request
just-in-time downloads of module JARs.