The difference was actually due to user confusion, not implementation. We used to be consistent with the markdown spec, but explaining markdown to nontechnical users who couldn't understand why their line breaks were being ignored was not worth it, so we switched to this custom dialect.
–
Ian HenryJan 31 '13 at 20:51