What about destroy method for kendoWindow?
It has strange behavior when there are opened a few modal windows in chain.
In case there are a couple of opened modal windows(win1, win2, win3, win4) after destroying one that was closed(win5) – two next in chain(win3 and win4) becomes enabled, instead of only the last one(win4).

Seems that the mistake lives here:

if (shouldHideOverlay) {
    that._overlay(false).remove();
} else if (modalWindows.length > 0) {
    windowObject(modalWindows.eq(modalWindows.length - 2), that.options.name)._overlay(true);                 
}

Why modalWindows.length - 2 but not modalWindows.length - 1 ?

I have to occasionally remove the contents of a div and generate another one with different kendo controls. The problem is controls like Datepicker or dropdownlist have their "dropdown portion" of the control in the body element of the page indepenedently, polluting the DOM unnecessarily. So the problem is whenever i remove the kendo controls from the aforementioned div these spans(the dropdown part of the controls) remain in the DOM. These spans cannot be distinguished from each other to define whichone belongs to the removed control so i cannot remove them manually. Repeating this action causes a lot of  orphaned spans which causes a memory leak.
Please implement a destroy method as soon as possible. Thanks!

Dear Kenshin, this request has reached 272 votes since February 22 and it's now ranked #4 of the most wanted feature (that's an obvious interest).  Can you please give us an update on Kendo's plan about this feature? 

Considering this feature have already reached 229 votes, and that it is linked to the requested feature #1 (Single Page Application), which have almost 400 votes, I think this feature should be your top priority.

This is crucial whenever building truly dynamic solutions. Please implement the earlier the better :).

Its a much needed one ... please release it asap.

absolutely agree, Kendo UI doesn't do everything I need, so I'm trying to incorporate several components in a SPA, this would be really helpful.

When using in combination with MVVM when you call kendo.bind() widgets are created for you when you have elements with a data-role attribute.
I would be very nice when kendo.unbind() would destroy all the widgets. It should not be the default I think, but it should be possible to explicitly opt-in for that.

This is definitely needed, especially since the grid doesn't allow changing of columns when rebinding data. I have to manually get rid of the grid and recreate it, which would be much simpler with a destroy method.