Using the same actionUid for both vm and vm template actions

I would like to be able to use a single action for both virtual machines objects and virtual machine template objects since they will be in mutually exclusive menus. I can see how this was done for the vsphere.core.vm.actions.rename action:

<!-- Rename -->

   <extension id="vsphere.core.vm.actions.rename">

      <extendedPoint>vise.actions.specs</extendedPoint>

      <object>

         <label>#{actionRenameVMLabel}</label>

         <description>#{actionRenameVMDescription}</description>

         <requiredPrivileges>VirtualMachine.Config.Rename</requiredPrivileges>

         <operationIds>Rename_Task</operationIds>

         <invoker>vsphere.core.vm.actions.rename</invoker>

      </object>

      <metadata>

         <objectType>VirtualMachine</objectType>

      </metadata>

   </extension>

but vise.actions.spec is not a supported extension point.

When I use the same actionUid in both vm and vm template menus it works well in the Flex client (except for disabling an action) but there are id conflicts in the html client.

My question is if the current 6.5 html client behavior is a bug or will same actionUid be allowed in mutual exclusive menus?

Attached is a modified plugin.xml from the 6.5 vsphere-wssdk-html sample to demonstrate the problem. I modified the actions to have two of the four actions available for vm templates. Notice that the two actions in the vm template menu so not show up in the menu for the vm even though they are defined.

Thanks for the help,

-Darrell