Why would you think you would want to do that?
You aren't inheriting anything you aren't already doing because of the ApplicationDbContext supplied.
Adding a second context may make sense in some situations, but chances are you will want to access the Identity fields, and if you are using a different context then you can run into problems with context coherency.
And, FYI, you don't put your DbSet's in the ApplicationDbContext's constructor.