Actually, it can be done, but not without making modifications to the aspnet_ procedures. Changing the procedures will let you do exactly what you need, however, be very aware that these changes will be lost, and are not really advised unless you pay careful attention to them when upgrading - as they are modifications of the core sql.
If you choose to share these users between portals, it can be done quite easily actually. The limitation is caused because the aspnet_ application id's are not shared between portals. DNN integrated with aspnet membership model by using the PortalID as the ApplicationName with the aspnet_application table. To share users, you basically need to comment out the reference to the ApplicationID from within the procedures that specifically deal with selecting the list of users, or fetching users by name. Once you comment out the specific areas where the Application ID is utilized, you will want to add a join in that joins on the UserPortal table - which will allow you to specify which users have access to which portal or portals.
It may take some time to look through and make some changes to the procedures, but it is well worth it - and it works! I have clients each with over 3,000 portals all sharing users between the portals.
Happy Nuking!