Thanks for reporting this, and kudos for figuring out the reason!
Apparently, common SSH servers accept both \r and \n, so we'll modify our behavior accordingly as well in the next release. (We will use a slightly different approach that would also work fine with SSH clients that send both \r\n in addition to \r or \n alone.)