Agreed, this should probably be fixed in one of the next few releases.
If this worries you for right now, you can directly access the Context object from the EFContextProvider instance, cast it to either an ObjectContext or a DbContext and call dispose on it.
As a side note:
From the Albarahi "c#
4.0 in a nutshell" book:
> Although DataContext/ObjectContext implement
IDisposable, you can (in general) get away without disposing instances.
Disposing forces the context’s connection to dispose—but this is usually
unnecessary because L2S and EF close connections automatically whenever you
finish retrieving results from a query <<