Issue title: TransactionTimeout coming out from EFUnitOfWork freezes web application
 Issue body: Hi everybody

Recently I was interactig with Microsoft Official Support in chasing some issue producing an application outage, requiring to restart iis application pool to get service available again.

This situation showed up three times in last two months, and had never seen before in a year and a half that application is using on production environment.

I was able to get two dumps on application's freezed state, and further research on this issue shows that there ara a lot of excecptions coming out from EFUnitOfWork, that seems to be in async mode pending to finish. Microsoft's support teeam help us on pointing out the stack execution related to the exception raising, and is as follow: please note that it was copied "as is" from microsoft's report, and seems to be upside down...

Castle.MicroKernel.Burden
System.Collections.Generic.List`1[[Castle.MicroKernel.Burden, Castle.Windsor]]
System.Object[]
Castle.MicroKernel.Burden
Castle.MicroKernel.BurdenReleaseDelegate
Castle.MicroKernel.Releasers.LifecycledComponentsReleasePolicy
System.Collections.Generic.Dictionary`2[[System.Object, mscorlib],[Castle.MicroKernel.Burden, Castle.Windsor]]
System.Collections.Generic.Dictionary`2+Entry[[System.Object, mscorlib],[Castle.MicroKernel.Burden, Castle.Windsor]][]
Abp.EntityFramework.Uow.EfUnitOfWork
System.Transactions.TransactionScope
System.Transactions.ContextData
System.Transactions.Transaction
System.Transactions.InternalTransaction
System.TimeoutException

Exception thrown is:
Exception Type        : System.TimeoutException
Message: Transaction Timeout
Exception Method Table: 00007FFB06E90AE8
Exception Object      : 000000078EBAFEB8
HResult: 80131505
InnerException: <none>
StackTrace:
<none>

Dump analysis shows up to 25k of this kind of exception on all .net heaps at the moment of app freezing.

Additional info:
Abp Version = 1.0.0
.Net Framework = 4.5.2
CLR version = 4.0.30319.36440

Would you think it is possible to be in presence of some issue related with async + TransactionScope + EFUnitOfWork?

Many thanks.
 Comments: 
 Comment 0: 1. That's not even a proper stack trace.
1. Upgrade your ABP version. So much has been fixed/improved since [v1.0.0](https://github.com/aspnetboilerplate/aspnetboilerplate/releases/tag/v116.69.203.115) (Sep 2016).
  Minimally, you should be able to upgrade to [v1.5.2](https://github.com/aspnetboilerplate/aspnetboilerplate/releases/tag/v1.5.2) (Mar 2017) without major changes.
 Comment 1: @juanmanuelrios there has been some improvements on the DI side. You can try to update your ABP version as @acjh suggested.
 Comment 2: Hi @acjh. Thanks for your reply.

I don't know why are you saying it is not a "proper" stack trace. I try to keep it "as is" from microsoft's support team response.  I was dgging around dump file after hang, but, to be honest, I can't get that stack trace. I saw other things but not the same as shown in this post.

Something I didn't say before is that all threads of the application pool are on Preemptive mode. None of them are in cooperative, this seems strange (at least for me). This situations is repeated on both application outages.

Anyway, I'll try to get ride on it by updating ABP to v1.5.2.

Thanks again.
 Comment 3: Hi @ismcagdas for your reply.

As you and @acjh suggested, I'll try updating ABP to v1.5.2.

I'll let you know in short if I can overcome this issue by doing this update.

Many thanks.
{'source': 'GithubIssues', 'repo_name_with_owner': 'aspnetboilerplate/aspnetboilerplate', 'issue_id': 351623775, 'repo_stars': 11273.0}