Admittedly, there was a change, but it was considered as an internal change with no practical effects. Now, your case exploits the difference.

To resume, the table clearing associated with an addTable invocation, in case the Engine were currently disconnected, was deferred until the first connection.
With Server-originated updates nothing has changed. Even in case of reuse of the same table with removeTable + addTable, you can cause the old table contents to be cleared as early as possible through setClearOnRemove, whereas, through setClearOnAdd, you can cause the old table contents to be cleared as late as possible.

However, your showValues occur after addTable and before the connection takes place and this now causes them to be cleared. Only performing the calls upon onStart would work.
We acknowledge that your use of showValues makes sense and will try to restore the original behavior. Sorry for the inconvenience.