dojoConfig is actually essential in the worker environment as there is no other way of telling dojo it's own root.  Scripts running via importScripts have no knowledge of their own execution path, they only path they know is the path to the parent page (or worker if a subworker).

This is a real pain but there is no way around it that I can see.  I guess that I need to add some comments to make this clear.

In my own use of this, I use a module, which passes the config to the worker then loads dojo into (see: [simpo/webworker](https://bitbucket.org/ssimpo/simpo/wiki/Worker)).  I think in the longterm something similar might be good for the Dojo Toolkit as it makes things transparent and polyfills browser differences.  I'm guessing that is not aligned with the current roadmap though and I imagine that it is important to get 1.10 out without distractions

As long as dojoConfig is supplied, Dojo seems to run quite well in workers.  It'll will need some notes in the documentation to tell be people how to get it working but should be reasonably easy.