Isn\'t there a more graceful way to have Entity Framework deployed with your UI project (specifically the sql server driver for EF: EntityFramework.SqlServer.dll) deployed w
Your reasoning is somewhat moot, but I can help clarify.
If you want to limit exposure to your EF context, then expose an interface via a unit-of-work/repository pattern. Create an abstraction layer on top of your EF implementation that gets injected via some DI construct like Ninject or Autofac.
Either way, the only way developers won't use your EF context is to be disciplined developers. Code reviews will help alleviate people doing dumb stuff.