This was something I experimented with as part of getting the Converter registration to be automatic. One problem we had in the configuration of the sample app and the KIM module was that the "packages to scan" needed to list all the KRAD packages or things would not work.
So, what I did was to create multiple lists of packages:
And then those are merged by a default bean into the single list: jpaPackagesToScan, which is used by the entity manager.
The problem I have at the moment is that merging bean is being defined in each of the modules because of the lack of an included file in which I can put the definition.
I also have a problem with most of the beans in the KIM and sample app module bean definitions, as they need to duplicate most of the data-access beans. (entity manager, transaction manager, etc...)
Since everything is in their own context, we should be able to provide an include file which creates all these beans, using properties (like the "module" packages to scan) which customize their behavior as needed.