I could have found more, but its a big org. Any examples I found that used other licenses where that way because they where related to something else that used a previous license (i.e. all TypeScript stuff is Apache2, hence any new TS is still be Apache2 for consistency).
A copyright license is not necessarily the same as a patent grant... Apache 2 does contain a patent grant, and an even bigger nuclear deterrent similar to Facebook's separate grant with MIT.
The MIT license is not a copyright license (though, copyright is claimed). It is a license for unrestricted dealings in the software subject to certain conditions (no warranty or fitness, appropriate notices given, etc.).
FWIW, my Android app's codebase has 18 Apache 2.0 dependencies, 1 MIT and 2 BSD. Maybe since the large libraries mostly use Apache 2.0, the smaller Android devs just follow suit?
The MIT license is problematic with software patents.
I see some projects moving to Apache2 for that reason (one prominent example here is Rust. They moved to an MIT/Apache2 dual licensing model).