Attempt to start javaws application that has been started recently and was not updated does not
require any download progress dialogs, security dialogs, etc.
If nothing is shown on the screen then there is no reason why javaws should trigger initialization of
Swing/AWT in the javaws secure thread.

Initial experiments using slightly modified refworkload tests show 10+% decrease (30 runs, significant)
of warm startup time if initialization of UI components does not happen (WinXP).

In more simplistic tests on Vista laptop similar of higher savings are observed too.
Using modified refworkload startup2 test avoiding creation of Swing components
till they are needed helps to reduce startup time of minimal webstart based swing application by about 13% (from 1662 to 1433 on test WinXP SP2 machine).