In general, the developers would not give attention and we as the project leads have to be constantly behind the developer to question that they have written the code to close the connections where ever they have used the ExecuteReader method.
This is the point that am trying to mention. Secondly, when ever a new connection is required by the another thread, that thread doesn't use the connection which is already opened. Thus, resulting many connections open during the project execution. Imagine
a situation where you have millions of users connected to the web app with such open connections!!!!???
I've came out with a wrapper for this kind of situation and wanted the EntLib Team should think about this issue