As discussed FTF, I think a better plan is to pin the loaded modules in memory until they have been referenced at least once from a browser.
Letting them be immediately unloaded before they are used and then reloading them seems inefficient and will annoy the user with duplicate warnings/errors from the module load. The downside of this approach is that any modules which are loaded but never referenced (such as from a launch config that is used for many different modules) will pin those modules in memory indefinitely, but I think that is the lesser evil. http://gwt-code-reviews.appspot.com/103801 -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
