If you're going to "delete" or destroy, then you should avoid closures :) no closures in Re: Tk::Table cell select/deselect or tk-frame-del-delmejo.pl ... but even though this code (delmejo) doesn't have closures, Tk::Frame does, so destroying frames (like Tk::Table) does leak small memory (Tk.pm implementation issue)

Reusing a table (or other widget) with a model/data is probably the best approach if memory is a concert in long-running-program ... see Re: perl tk mainwindow capability (virtual tree widget, huge amounts of data, pageination)