Reviewing through your description it appears you are running into a bug tracked for the Jive 6 platform, JIVE-44187, which is listed as opened/unresolved. Additionally, running through this test in a current release of the platform (Jive 8) the behavior is no longer occurring. As such an upgrade is recommended to resolve this behavior.
Yes, I opened an internal case and I was referenced to the same bug. In any case I was able to workaround this.