Hi Scott Lavender,
Yes, we are aware of this problem and we have already resolved it. The problem comes from an incorrect target name in our Disabled visual state. You can either experience this problem if you explicitly disable any of the CoverFlowItems, or you use ChildWindow control, when opened, disables all controls in the current application. To get rid of the problem download our latest internal build in Friday that will contain the fix. Until then please excuse us for it, and we hope this won't be a showstopper for you.
If you have any other concerns, please feel free to contact us again.
the Telerik team