We didn't find much information about the Personality folders created per user profile, but we figured out that those folders contain very similar information as the register entries for the user profile. It seems to me that View checks into that folder when the users logs in. If ther personality folder is not there, View assumes that the users is logging in for the first time so it creates  a new profile instead of using the existing profile contained in the persistan disk before recomposing the pool. Our solution to the issue was to recreate the master VM and install the View agent again. Reinstalling the agent in the problem master wasn't just enough.