@mathew thank you for reporting this behavior! LightDB State can handle arrays, but what you are observing is a confusing behavior in how the console interacts with the LightDB State API. The console always replaces the entire LightDB State object with the provided values, which causes nested child arrays to be converted to the indexed map format.
We are looking into addressing this behavior as it is not intuitive. However, in the meantime you can work around this by calling the API directly with the specific path for the array and the array itself as the top-level value. See the following example: