Wicket DateTimeField / DatePicker creates a memory leak on the browser when rerenderd using ajax requests

When a wicket DateTimeField is repeatedly added to a page using AjaxRequestTarget#addComponent(..) it creates a memory leak on the browser. This will eventually cause memory starvation
on the client machine.

The error can be reproduced by using a DateTimeField component that updates itself using the AjaxSelfUpdatingTimeBehavior.

DateTimeField field= new DateTimeField("field", new Model<Date>(new Date()));
field.add(new AjaxSelfUpdatingTimerBehavior(Duration.seconds(0.5)));
add(field);

Running this for just an hour or so clearly shows that the browsers do not free up resources. The problem seems to be related to how wicket-date.js reinitializes a new Yahoo Yui Calendar widget using the same element id on each rerendering.