You want to keep the entity definitions also separated? Do you use a single session with multiple assemblies?
LLBLGen Pro supports multiple catalogs, and you can define in the project multiple groups which can represent multiple vs.net projects (assemblies), so you can define the entity (e.g. 'Product') multiple times in the project (e.g. in each group) and map it to the same target. This has the advantage that when the target table changes, all the entities mapped onto it are validated against it.