Thanks for responding LucD,
Yes, there is a FreespaceGB property, I tested it out a piece at a time, I also see the...I guess old FreespaceMB one. I can see how initially the one particular datastore may have been selected over and over, but then it only had about 73GB free, and there were datastores that had easily over 800GB free, when the script was still putting everything on that one particular one. I still have the error messages up showing "Insufficient disk space on datastore 'name'", and I can see that at least 5 VMs tried to get moved there, even though it didn't have the space to support them. It just looks like it should work correctly.