Unfortunately I could not upload a simple test application due to its size (no maven applied..) but I could eventually if the size of >10 MB is allowed.
Anyway a test application can be easily built in principle because it's just a matter of repeatedly displaying a Trinidad table and checking back in a profiler that its internal data are not released i.e. precisely speaking, SortableModel and RowKeySetImpl.
These two keep growing the following way: 1 instance of SortableModel per table and 2 instances of RowKeySetImpl per table.
So the leak growth follows the scheme 1/2, 2/4, 3/6, 4/8 and so on.