Possible scalability problem in ASP.NET projects which use Entity Framework or other ORM solutions.

Recently I've come across a very useful article by Michael K. Campbell which describes a very common mistake in the architecture of ASP.NET application that uses EntityFramework or any other ORM solution.

Since I met (and even did :)) the similar mistake before I decided to share a link to that article here.
Enjoy!