IServiceScopeFactory - for background task scoping.

I am using entity framework core via dependency injection. I have noticed that after background tasks executing which utilize my DB context run for a period of time, i start getting some errors which i think relate to the connection not being closed properly - connection pool fills up?

I am trying to work out what is the best scoping to use for background tasks. Do i need to implement IServiceScopeFactory - something like this inside the background task. Or does hangfire already set the scope when executing background services.

```
using (var scope = _serviceScopeFactory.CreateScope())
{
var context = scope.ServiceProvider.GetRequiredService();
// now do your work
}

```
I guess it would be good to know the inner mechanics.

Review how Hangfire scopes background jobs and how IServiceScopeFactory is used with an Entity Framework Core DbContext. Reproduce the reported long-running background-task errors and document the expected scope and connection behavior; done when the cause and recommended scoping are clear.

Written by the indexing model from the issue text.