Hi Mnahum,
Anecdotal evidence in my case seems to be that if I upgraded directly from 5.0.1 to 5.0.3 then I get the issue, I tried it twice and got the same results - although it sometimes took a few hours for the issue to appear (one time only 15 minutes, and I was doing light work - just emails.)
For some reason, this time, going from 5.0.1 > 5.0.2, and then from 5.0.2 > 5.0.3 seems to have resolved the issue for me.
I made sure I re-installed the VMware tools on each upgrade.
I did all the normal things people advise ... disk check, permissions check, PRAM reset, Safe boot ... but in the end it seems jumping from 5.0.1 directly to 5.0.3 seems to have been the issue.
VMware tech guys took a look at my logs and said the VM was taking 100% CPU at the time it hung and asked for me to switch on Performance debugging - however so far no problems to report back to them.
I'm crossing my fingers 