This results in a "clean" rejection, where the rejected don't have traction for arguing that they'll "change" or "not do that again" when the rejecters simply don't want to deal with them anymore (for whatever their reasons, rational or otherwise). It's certainly not productive from the rejected's perspective, they truly might not know what they did to offend/displease their coworkers, but it can prevent awkward situations.
By not including "real" reasons for rejected, your signaling the the rejected that your not interested in conversing about your decision and that your decision is final, regardless of the logic used to reach it (I think all of these are implicit properties when you don't share your logic behind a decision).
As an added bonus, the same strategy works when rejecting people in your personal life, so there's also the societal familiarity/subtext that comes along with the generic rejection that can further emphasize the undesirability of continued interaction and the finality of the decision.
I still hate it, but I understand it.
He actually missed his start day, without notice, now that I remember, and started late.
I looked up his music scene and realized he'd been at a rave in another state all weekend, and was clearly hungover and irritable.
Although, I must say, he did seem to be a fairly decent developer, as far as I could tell by talking with him over two days.