We make extensive use of the ScheduleView in one of our business applications.
Unfortunately there seems to be a major memory leak within the RadScheduleView component, which leads to a massiv performance degeneration of the silverlight UI elements in general.
A simple demonstration would be the TV Schedule Demo: http://demos.telerik.com/silverlight/#ScheduleView/TVSchedule
A few minutes of scrolling left and right to force the component to redraw the appointments is sufficient. It seems like UI-components for the appointments - which should be discarded when scrolling out of view - are kept in memory and new UI-components are created whenever an appointment scrolls into view.
After a while silverlight in itselfs becomes sluggish, creating of new UI-elements takes seconds - the UI becomes unresponsive.
This is a huge problem for us, as it renders our application unusable after a few minutes of work.
There is a known bug related to grouping, but this behavior is apparent even when no grouping is used.