First, I'm not aware of a bypass for this behaviour I'm afraid 
Unless you make the AD queries directly. The Quest AD snapin could help here.
Secondly, and in the defense of PowerCLI, this is imho a problem with the RetrieveUserGroups method, which the PowerCLI cmdlet uses under the covers. That method apparently doesn't optimise the LDAP calls to AD.