The script runs without error, just the results that are returned are different (and incorrect) when run from the PowerCLI shortcut vs the standard PowerShell shortcut. I discovered this issue because I have a native PowerShell script that has been working for some time and has not been changed; and needed to feed the output to a new PowerCLI script to take actions in vCenter. The PowerCLI script was not providing the expected behavior and running just the native Powershell script from the PowerCLI shortcut initiated session immediately showed why (the PowerCLI script was acting on an incorrect set of data).
I'll follow the suggestions posted to see if I can track it down; thanks.