When using modules together with the "-module-output" compiler option, there are differences between loading a module with "autoLoad=true" or "autoLoad=false"

When loading modules I get browser errors if "autoLoad=true" for my modules, but all works if I manually call "loadModule()". I am using the "-module-output" compiler option so the modules are output in "modules/module1" and "modules/module2" directories. So the result is that dependencies are located in the final application in multiple locations. (At least once for each module that uses them)

If I user autoLoad=true I get a browser error for every time a type is loaded that has been previously loaded by the main application or a previously loaded module.

However if I select "autoLoad=false" and explicitly load the module by clicking a button all seems to work and I don't get the error.

I would at least expect consistency in this matter.