I am seeing this same behavior with all the current 5.1 products using Orchestrator... what gives? Is this a confirmed bug? Is this by design? Am I doing something wrong on my side possibly?
I also posed a question here for full details and my sample code http://communities.vmware.com/message/2180252#2180252