You could use the 'type' parameter to the notification to hold the name of the module to load and let the body be the reference to the ModuleLoader to load said module into.
The way I got around it was inside my controller, I loaded the module using ModuleManager.getModule(), registered the module with the moduleFacade, then sent a LOAD_MODULE_SUCCESS notification with the IModuleInfo as the body. The mediator that sent the request notification originally, is listening for that notification and then can do something like:
app.container.addChild( (notification.getBody() as IModuleInfo).factory.create() as Module2 );
--The positive, no moduleloaders to pass around, clean separation of controller from view components.
--The negative - The same notification is sent regardless of which module was loaded making loading multiple modules simultaniously ugly. (the mediators would have to inspect the module, or the controller could add the module name in the notifications type field.