As part of 4.0, we added change streams notifications for database drops and consciously decided that single-collection change streams should remain open if the collection never existed (some discussion in the review for SERVER-35029).

This is different behavior in 3.6 as the single-collection change streams are invalidated if the database is dropped. We should decide on a consistent approach and document it.