The update on this is that it turned out to be a Cisco bug...

Still, blame the new gadget for exposing it

Hugo