Last I checked, that was just wrong on Unix; it kills only the shell. This is probably because someone did not consider that most modern shells support job control, and therefore start commands in their own independent process groups. (Or assumed that this does not happen with "sh -c"; I would have to test specific shells --- and versions! various bash versions can behave quite differently and often have bugs lurking in the dark corners --- to see if this applies.)
--