Improperly unloaded Profilecontainer leads to wrong RefCount and prohibites relogin

We are excessivly using Profile Containers (about ~90 so far) for terminal server accesses. Some of the single profiles are used by multiple clients who share the same room / building. Over the time we noticed a strange side effect, most of the time happening on userprofiles of departements doing shiftwork or having a quite bad vpn connection which leads to a bad reference count in registry where the terminalserver(s) (Windows Server 2019 Std. DC) think that there is still one user logged in with that container, which is not true. That means the mounted user profile folder //Users/MountedProfile is blocked by not existing processes, which means it can't be removed, nor can the user login as the folder is not accessable anymore. The only solution is to switch the user to another terminalserver or reboot the server to be able to delete the still mounted profilefolder. I wish to ask if anyone has experienced a similar behaviour and/or found a workaround to not let that happend again? Thanks for the help .. :-)