Do I need to cleanup runtime binding container and iterators?

Question

If I create a runtime binding container and iterator in a JSF session bean as follows:
FacesContext facesContext = FacesContext.getCurrentInstance();
ValueBinding valueBinding = facesContext.getApplication().createValueBinding("#{data}");
BindingContext bindingContext = (BindingContext)valueBinding.getValue(facesContext);
// To create JUIteratorBinding, we need the following objects
DCDataControl dataControl = bindingContext.findDataControl("MyDataControlName");
ApplicationModule appModule = (ApplicationModule)dataControl.getDataProvider();
DCBindingContainer bindingContainer = new DCBindingContainer();
// Create dynamic iterator.  Need to set bindingContainer otherwise executeQuery throws exception
JUIteratorBinding iterator = new JUIteratorBinding(bindingContext, dataControlName, "MyViewObjectName", "MyIteratorName", -1);
iterator.setBindingContainer(bindingContainer);....do I have to later clean down the iterator and binding container from the data control to release the memory (and what calls do I need to make), or once the objects fall out of scope in my code are they marked for GC?
CM.
PS. JDev 10.1.3.1, ADF BC and JSF

Answer 1

Hi Steve, thanks for the follow up.
I'm coding a dynamic menu <af:page> control that maps to the MenuTreeModelAdapter (session bean) as detailed in the JDev 4GL/Forms guide.
I've made a change that instead of loading the menu items from the hardcoded faces-config.xml file, they're actually sourced from the database via the code above, which is placed in the MenuTreeModelAdapter constructor. As the <af:page> tag exists on a number of pages, and thus the MenuTreeModelAdapter may be instantiated for the first time from a number of different locations, I can't hard-code the binding container or iterator into any single pageDef file. Thus I dynamically construct it in the constructor when the session bean is created for each user. I require a session bean as the menu items are different for each user.
However I'm concerned once I've created the binding container and iterator, that even though the session bean may become invalidated, the 2 binding layer constructs may remain, consuming resources.
Thanks for your assistance.
CM.