The idea would be to help determine the optimum stack size for a given Java application.
One thing that could be done with this information create a range-table of stack sizes which the threads could modify as they exit and which could be dumped periodically and at application exit.
EDIT: This is in the context of running on customer machines with real workloads which I can't get profiler access to.
EDIT2: In response to one answer, at (IIRC) 256Kb per thread, I have wondered for a while now how close to the reality of what's need that is (I also wonder if it's not very relevant because it's allocated on demand). We have an application server which is based on message passing and highly threaded and runs on everything from an ARM handheld to octo-core Linux, to midrange and mainframes - it would be good to have a feeling where (and if) we can trade stack space for heap on systems with many message handlers.
There are some similar questions which are of interest, but they are native/os-specific: