There is 84% footprint regression in NodeMemory.TableColumn benchmark occurred in one of 3 builds:
8.0-controls-scrum-622, 623 or 624. There are no builds 622 and 624 available in hudson, the history of changes is
 #624 (Jun 13, 2013 8:14:00 AM)
    RT-31062 - ControlResources : update review — mickf / detail

 #622 (Jun 13, 2013 1:23:28 AM)
    RT-31016 javafx.scene.control.TableView: column headers shoud appear
    RT-30363 Region calls requestLayout too aggressively — Martin Sladecek / detail


According to MemoryAnalyzer the reason seems to be related to extra
 com.sun.javafx.scene.control.skin.TableColumnHeader objects are being created.


I did run the attached TableColumnMemTest with builds 621 and 624 till the test fails with OutOfMemory
and heap dumps contain quite different number of TableColumnHeader objects:

#621:
 1,600 javafx.scene.control.TableColumn
 3,191 com.sun.javafx.scene.control.skin.TableColumnHeader

#624:
   310 javafx.scene.control.TableColumn
 6,412 com.sun.javafx.scene.control.skin.TableColumnHeader


To reproduce the issue run TableColumnMemTest with build 621 and 624 (or the latest available from controls-scrum):
> java -XX:+HeapDumpOnOutOfMemoryError -Xms64m -Xmx64m -client -cp "JFX_HOME/rt/lib/ext/jfxrt.jar;./" TableColumnMemTest

then look at created heap dumps using Eclipse memory analyzer of jhat.