@zachraduban I am not exactly sure that I understood you here, but i will give it a try.
You can omit the required from your maven dependency scope, and handle the unavailability of the services programatically.
You can use
@SprinngBean(required=false,value="moduleBService") in your controllers, or handle null pointers.
// your code here
Yes you can opt, to omit the scope required, but then you have to be extra-careful when using the beans from the module.