I am using Entity Framework for my Custom MembershipProvider, and I like to attach my DataContext to a User Session when possible as per the West Wind article below but Sitefinity is consistently overwriting HttpContext.Current.Items. Do you have any ideas on why this may be? anything I may do to prevent it? or know of another constantly present object where I may be able to store the DataContext? Once I do finally catch a debug turn where my DataContext is still in HttpContext.Current.Items I get the error "The ObjectContext instance has been disposed and can no longer be used for operations that require a connection."