Thanks for bringing this to our attention. Indeed we have changed that navigation behavior, however the one in your scenario is not expected one, so I logged it on internal backlog. You can achieve the old behavior by simply setting the KeyboardNavigation.TabNavigation property to continue:
Hope this helps. I have also updated your Telerik points for your involvement.
Check out the Telerik Platform - the only platform that combines a rich set of UI tools with powerful cloud services to develop web, hybrid and native mobile apps.