This sounds like a bug which should be submitted to SDL Customer Support. Does the behavior differ with IE, Chrome and FF?
Unless support can provide a hot fix, I think your only option is to filter out the lone BR (as Frank suggested) using the filtering XSLT. The default XSLT filter used when creating a new rich text field has this filtering included as shown below (last <template>
node).
<stylesheet version="1.0" xmlns="http://www.w3.org/1999/XSL/Transform">
<output omit-xml-declaration="yes" method="xml" cdata-section-elements="script"></output>
<template match="/ | node() | @*">
<copy>
<apply-templates select="node() | @*"></apply-templates>
</copy>
</template>
<template match="*[ (self::br or self::p or self::div) and normalize-space(translate(., ' ', '')) = '' and not(@*) and not(processing-instruction()) and not(comment()) and not(*[not(self::br) or @* or * or node()]) and not(following::node()[not( (self::text() or self::br or self::p or self::div) and normalize-space(translate(., ' ', '')) = '' and not(@*) and not(processing-instruction()) and not(comment()) and not(*[not(self::br) or @* or * or node()]) )]) ]">
<!-- ignore all paragraphs and line-breaks at the end that have nothing but (non-breaking) spaces and line breaks -->
</template>
<template match="br[parent::div and not(preceding-sibling::node()) and not(following-sibling::node())]">
<!-- Chrome generates <div><br/></div>. Renders differently in different browsers. Replace it with a non-breaking space -->
<text> </text>
</template>
</stylesheet>
` using either a custom XSLT filter or an event system. – Frank van Puffelen Nov 15 '12 at 12:15
' tag is left there in the first place? This seems like a bug. – Kevin Brydon Nov 15 '12 at 12:25