VMware support came back to me and said it is a known bug in 5.1 and should be fixed in the future. There is also a KB article for this that looks like it was updated July 24th. Not sure if this is due to me opening the case or that KB has been out there and I never noticed it -
http://kb.vmware.com/kb/205291