This has been already fixed in #377

This issue is not fixed.
The dependency is updated but AndroidView doesn't specify an onReset implementation which is necessary for enabling re-use of the underlying View.

From the javadoc:

By default, AndroidView does not automatically pool or reuse Views. If placed inside of a reusable container (including inside a LazyRow or LazyColumn), the View instances will always be discarded and recreated if the composition hierarchy containing the AndroidView changes, even if its group structure did not change and the View could have conceivably been reused.
Views are eligible for reuse if AndroidView is given a non-null onReset callback. Since it is expensive to discard and recreate View instances, reusing Views can lead to noticeable performance improvements — especially when building a scrolling list of AndroidViews. It is highly recommended to specify an onReset implementation and opt-in to View reuse when possible.

The current implementation looks like this which isn't specifying an onReset implementation (v3.0.0):

AndroidView(modifier = modifier, factory = { mapView })

Currently, if the GoogleMap composable is placed in a LazyColumn, the mapView is re-created/disposed for every item while scrolling.

This is very important for our app because it shows multiple maps in a scrollable column. Meanwhile we're stuck with RecyclerView.

More info is documented in: https://developer.android.com/jetpack/compose/migrate/interoperability-apis/views-in-compose#androidview_in_lazy_lists Basically you'll need to update the implementation to provide a non-null onReset value on the AndroidView overload.