I used the script from the following link below to identify orphaned vmdk's in my environment. I was able to remove all the orphaned vmdk's except for a series of them for a virtual machine. We use TSM to backup our vm's and at one point it went crazy and created a lot of vmdk's while snapshotting and didn't remove them. This machine with the orphaned vmdk's appears to be one of them. When I saw these files I initially attempted a consolidation even though vCenter didn't indicate it needed a consolidation. I also took a snapshot and deleted it to see if it would somehow remove the orphaned vmdk's but it didn't. I compared the vmdk's against the vmx manually to ensure they weren't being used by the vm and they aren't. So I went to delete them, but it won't let me. Anybody have an idea about what is going on with these vmdk's. It acts as if the files are still in use but that script indicates that they aren't.
http://virtuallyjason.blogspot.com/2013/08/orphaned-vmdk-files.html