Ok, found a fix for this but unfortunately I'm not sure about "why" this fixed the problem.
I set the RegisterWithScriptManager property to false and the problem went away.
I'm slightly confused though, by default it is set to true and the control will complain about not having a script manager inserted on the page. Surely by being set to true it does not need a client script manager block as it is using something on the server side????