This is something that is not directly exposed through the context, however there is an easy fix you could implement. The context has an underlying scope that you can access. You have to implement a partial class of the context and in it a property that return an IObjectScope that it would get from the protected method GetScope().
Then you could easily call the old scope.Transaction.Flush() and be sure that context.ClearChanges would revert the changes to the database. We will be considering exposing this in the context so that you needn't use the scope.
I do hope this helps.
the Telerik team
Do you want to have your say when we set our development plans?
Do you want to know when a feature you care about is added or when a bug fixed?
Telerik Public Issue Tracking
system and vote to affect the priority of the items