Haven't found it yet. Nobody else is hitting this either apparently. Manually limiting the # of cores on GHC pretty much removed the issue for us, although it doesn't give me the sense of closure I was hoping for.

I'm vaguely suspecting some sort of resource contention issue. A good way to figure that out would be to run a profiled build with that many cores, assuming that's at all possible.